Startup control of devices

ABSTRACT

Controlled startup of devices is based on dynamic statistical predictions. Timely startup of onboard associated vehicle devices is based on dynamic statistical predictions and driver proximity to the vehicle. An apparatus for timely startup includes an interface operatively coupled with a power consuming device and control logic coupled with the interface. The control logic is operable in a first mode to perform processing for determining a presence of a first condition of the vehicle, and to selectively activate the power consuming device of the vehicle, via the interface, responsive to determining the presence of the first condition. The control logic is operable in a second mode to suspend, via the interface, the processing for determining the presence of the first condition of the vehicle. The control logic selectively transitions between the first and second modes in accordance with a stochastic modeling of the presence of the first condition over time.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation application of U.S. patent application Ser. No.14/024,080, filed Sep. 11, 2013.

TECHNICAL FIELD

The present disclosure relates generally to timely startup control ofdevices relative to anticipated need for use of the devices.

BACKGROUND

Motor vehicles are increasingly equipped with electronic devices thathave sophisticated software applications which need to boot up andbecome functional in a timely manner to satisfy instant-on experienceexpectations and to satisfy stringent vehicle communication and controlperformance requirements. Such electronic devices include in-vehicleinfotainment, navigation, telematics, onboard communication gateways,vehicle safety communication and control systems and the like.

There may be insufficient time for a device and all its software andapplication modules to become fully functional before the vehicle or itsdriver expect to use the functions provided by the device. Consequently,many functions, which rely on sophisticated software, cannot becomefully functional in a timely manner and ultimately result in driverdissatisfaction.

As software in automotive electronic devices becomes more complex, bootup times typically increase accordingly. Shortening just the softwarestartup time alone may be insufficient to ensure that a device canbecome fully functional in a timely manner. Detection of remote driverdoor unlock and/or physical door opening events provides mere blindstartup control of devices and thereby may consume battery powerneedlessly if the driver has no intention of ever using the device ornever intends to start the engine of the vehicle. Some proposed schemesdraw continuous power and thereby unnecessarily deplete the mainbattery.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings incorporated herein and forming a part of thespecification illustrate the example embodiments.

FIG. 1 is a flowchart of basic operating states of an associated motorvehicle and conditions for transitions between the states.

FIG. 2 is a block diagram illustrating a Power Management Module (PMM)operable with components of an associated motor vehicle in accordancewith the example embodiment.

FIG. 3 is a functional block diagram showing the PMM of the exampleembodiment in use with selected components of an associated motorvehicle.

FIG. 4 is an example methodology of operating the PMM in an ignition ONstate of the associated motor vehicle.

FIG. 5 is an example methodology of operating the PMM in an ignition OFFstate of the associated motor vehicle.

FIG. 6 is an example methodology of operating the PMM in an Active Modeduring the operation shown in FIG. 5.

FIG. 7 is a high level functional flow block diagram showing the PMM inan Active Mode in accordance with an example embodiment.

FIG. 8 is a control diagraph showing operation of the PMM in accordancewith an example embodiment.

FIG. 9 is a chart showing several operational modes of the PMM inaccordance with an example embodiment.

FIG. 10 is a state transition diagraph showing several power modes ofthe PMM in accordance with an example embodiment.

FIG. 11 is a state transition diagram between power modes of the PMM inaccordance with an example embodiment

FIG. 12 is a block diagram illustrating an example embodiment of acomputer system upon which an example embodiment can be implemented.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

The following presents a simplified overview of the example embodimentsin order to provide a basic understanding of some aspects of the exampleembodiments. This overview is not an extensive overview of the exampleembodiments. It is intended to neither identify key or critical elementsof the example embodiments nor delineate the scope of the appendedclaims. Its sole purpose is to present some concepts of the exampleembodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

In accordance with embodiments herein, one or more devices and softwaresupporting the one or more devices are timely initiated from an off orsleep mode or condition and thereby allowed to boot up and become fullyfunctional prior to an anticipated need for use of the devices. In theexample embodiment, one or more onboard vehicle devices and softwaresupporting the one or more onboard vehicle devices are timely initiatedfrom an off or sleep mode or condition and thereby allowed to boot upand become fully functional prior to a driver enters the vehicle.Overall battery power consumption by the device while the vehicle is inan ignition-off state is also minimized.

In accordance with an example embodiment, there are disclosed hereintechniques wherein selected components of an associated motor vehicleare initiated or activated in a timely manner relative to their expecteduse and/or need.

In accordance with an example embodiment, there is disclosed herein anapparatus comprising an interface operatively coupled with a powerconsuming device of an associated motor vehicle, and control logiccoupled with the interface. The control logic is operable in a pluralityof modes comprising at least a first mode and a second mode. The controllogic is operable in the first mode to perform processing fordetermining a presence of a first condition of the associated motorvehicle. The control logic is operable in the first mode to selectivelyactivate the power consuming device of the associated motor vehicle, viathe interface, responsive to determining the presence of the firstcondition. The control logic is operable in the second mode to suspend,via the interface, the processing for determining the presence of thefirst condition of the associated motor vehicle. The control logicselectively transitions between the first and second modes in accordancewith a stochastic modeling of the presence of the first condition overtime.

In accordance with a further example embodiment, there is disclosedherein a method comprising operating control logic in a plurality ofmodes comprising at least a first mode and a second mode; performingprocessing by the control logic operating in the first mode fordetermining a presence of a first condition of an associated motorvehicle; selectively activating by the control logic operating in thefirst mode a power consuming device of the associated motor vehicle, viaan interface coupled with the control logic and operatively coupled withthe power consuming device, responsive to determining by the controllogic the presence of the first condition; suspending by the controllogic operating in the second mode the processing for determining thepresence of the first condition of the associated motor vehicle; andselectively transitioning the control logic between the first and secondmodes in accordance with a stochastic modeling of the presence of thefirst condition over time.

In accordance with yet a further example embodiment, there is disclosedherein logic encoded in one or more tangible non-transientcomputer-readable media for execution by a processor and when executedby the processor the logic being operable to operate control logic in aplurality of modes comprising at least a first mode and a second mode;perform processing by the control logic operating in the first mode fordetermining a presence of a first condition of an associated motorvehicle; selectively activate by the control logic operating in thefirst mode a power consuming device of the associated motor vehicle, viaan interface coupled with the control logic and operatively coupled withthe power consuming device, responsive to determining by the controllogic the presence of the first condition; suspend by the control logicoperating in the second mode the processing for determining the presenceof the first condition of the associated motor vehicle; and selectivelytransition the control logic between the first and second modes inaccordance with a stochastic modeling of the presence of the firstcondition over time.

Detailed Description of Example Embodiments

This description provides examples not intended to limit the scope ofthe appended claims.

The figures generally indicate the features of the examples, where it isunderstood and appreciated that like reference numerals are used torefer to like elements. Reference in the specification to “oneembodiment” or “an embodiment” or “an example embodiment” means that aparticular feature, structure, or characteristic described is includedin at least one embodiment described herein and does not imply that thefeature, structure, or characteristic is present in all embodimentsdescribed herein.

In general, the embodiments herein provide timely startup control ofdevices relative to anticipated need for use of the devices. The startupcontrol may include the application and/or removal of power relative tohardware and may include the booting up and/or down of software or otherlogic. In the example embodiment, the devices are onboard motor vehicledevices. However, it is to be appreciated that the embodiments of theclaims herein are not limited in any way to the example embodiments butrather are to be interpreted to cover timely startup of any devicesbeyond those for vehicles in any application. That is, the embodimentsherein can be applied to management of startup and shut-down ofelectronic systems in homes, offices, factories or anywhere timelywakeup or power management is desired.

In an embodiment, proximity of a driver relative to a motor vehicle isdetected and selectively used with other factors to intelligently timelypower up and/or down selected devices of the motor vehicle and softwareand application modules of the devices in accordance with the proximitydetection.

An embodiment herein uses one or more statistical models to dynamicallypredict an anticipated need for use of devices and to control the timelystartup of the devices relative to anticipated need for use of thedevices thereby ensuring timely boot-up and eliminating or reducingunnecessary or premature power-up of the device and software andapplication modules of the devices.

A further embodiment herein operates in multiple power modes to balancepower savings and the ability to timely start up the one or more devicesand their respective software and application modules. Statisticalmodeling techniques are selectively used to determine when a device, itssoftware, and its application modules should enter into or transitionbetween the power modes and how long to operate in each power mode.

In an embodiment a supervisory power management module may becentralized or distributed and selectively operates in alternate activeand power-saving modes, and determines when it should enter into, andhow long it should stay in, each of the one or more power-saving modeswithout jeopardizing its ability to timely start up the devices underits power management.

With reference now to the drawing Figures, wherein the showings are forpurposes of illustrating example embodiments only and not for purposesof limiting same, FIG. 1 illustrates a flowchart of a basic operatingmethod 100 of an associated motor vehicle. As shown, the associatedmotor vehicle enters into one or more basic operating states selectivelytransitions between the states. In a first mode of the associated motorvehicle, the vehicle is in an ignition OFF state 110. In a second mode120 of the associated motor vehicle, the vehicle is in an ignition ONstate 120. The associated motor vehicle may operate in one or more otheradditional modes or states as well but for purposes of describing theexample embodiments herein, the ignition ON and OFF states aresufficient.

At step 112, the ignition key or equivalent system of the associatedmotor vehicle is transitioned to an ON position or condition whereby theassociated motor vehicle transitions from the ignition OFF state 110 tothe ignition ON state 120. Similarly, at step 122, the ignition key orequivalent system of the associated motor vehicle is transitioned to anOFF position or condition whereby the associated motor vehicletransitions from the ignition ON state 120 to the ignition OFF state110.

In accordance with embodiments herein, signals may be received from theassociated motor vehicle indicating the current state of the associatedmotor vehicle. Alternatively, embodiments herein may query theassociated motor vehicle for its current operating state from time totime as appropriate. Yet still further, the embodiments herein may beintegrated, more or less, with selected components of the associatedmotor vehicle to more easily and quickly determine the currentoperational state of the vehicle in a manner that is transparent to thevehicle.

FIG. 2 is a block diagram illustrating a Power Management Module (PMM)200 in accordance with the example embodiment operable with componentsof an associated motor vehicle. The PMM 200 comprises a first interface202 coupling the PMM 200 with an associated source of power such as, forexample, the battery of the associated motor vehicle, a second interface204 coupling the PMM 200 with a switch disposed between the battery ofthe associated motor vehicle and one or more hardware modules of themotor vehicle wherein the switch controls power to be applied to themodules in accordance with signals from the PMM, a third interface 206coupling the PMM with one or more software and/or application modules ofthe associated motor vehicle corresponding to the one or more hardwaremodules, and a transceiver unit 220 including an antenna 222 forselective communication with one or more portable electronic devices ofa user of the associated vehicle. The PMM of the example embodimentfurther comprises control logic 210 coupled with the first, second, andthird interfaces, wherein the control logic is operable to receivesignals from the associated motor vehicle to discriminate between theignition ON and ignition OFF states, and to determine transitionstherebetween. The control logic is further operable to control thetimely startup and intelligent power down of the one or more softwareand application modules of the associated motor vehicle and to controlpower selectively applied to the one or more hardware modules of theassociated motor vehicle in accordance with embodiments to be describedin greater detail below. “Logic” as used herein, includes but is notlimited to hardware, firmware, software and/or combinations of each toperform a function(s) or an action(s), and/or to cause a function oraction from another component. For example, based on a desiredapplication or need, logic may include a software controlledmicroprocessor, discrete logic such as an application specificintegrated circuit (“ASIC”), system on a chip (“SoC”), programmablesystem on a chip (“PSoC”), a programmable/programmed logic device,memory device containing instructions, or the like, or combinationallogic embodied in hardware. Logic may also be fully embodied as softwarestored on a non-transitory, tangible medium which performs a describedfunction when executed by a processor. Logic may suitably comprise oneor more modules configured to perform one or more functions.

With reference next to FIG. 3, as noted, in the example embodiment, thePMM 200 manages power up of one or more devices of the associated motorvehicle, and bootup and software startup procedures of the one or moredevices as the driver is approaching the associated vehicle from adistance to ensure adequate time is available for the one or moredevices to become fully functional. In this disclosure, any electronicdevice managed by the PMM will be referred to as a “device” and it is tobe appreciated that the PMM can manage one or multiple devices. Inaddition, it is to be appreciated that the PMM can be a separate entityfrom the device or it may be implemented as an integral module insidethe managed device and/or distributed between several managed devices.

FIG. 3 is a functional block diagram showing the PMM 200 of the exampleembodiment in use with selected components of an associated motorvehicle including in the example a set 300 of devices including hardwaremodules 320 and software modules 330 corresponding to the hardwaremodules, a power disconnect unit 302, and a power source 304. The firstinterface 202 (FIG. 2) couples the PMM 200 with an associated source ofpower such as, for example, the battery 310 of the associated motorvehicle via a power feed connection 312. The second interface 204 (FIG.2) couples the PMM 200 via a power switch control signal line 314 withthe power disconnect unit 302 disposed between the battery 310 of theassociated motor vehicle and the set 300 of one or more hardware modules320 of the motor vehicle wherein the power disconnect unit 302 isoperable as an electrical switch to control the application of power tothe set 300 of modules of the vehicle in accordance with signals fromthe PMM.

In the illustrated embodiment, the power from the battery 310 isdelivered to the hardware modules 320 by a pair of power delivery lines316, 318 whereby power may be delivered to the device hardware modules320 which are grouped into mission-critical hardware modules 322 andnon-mission-critical modules hardware modules 324. The power to themission-critical modules and the non-mission-critical modules iscontrolled by separate switches on the power supply line. Similarly, thesoftware and application modules 330 of the set 300 of devices aregrouped into mission-critical software modules 332 andnon-mission-critical modules software modules 334 in a way thatmission-critical software modules can be started before and/orseparately from non-mission-critical software modules as maybe necessaryor desired. Along those lines, startup control of the software modules330 is delivered from the PMM 200 using the third interface 206 (FIG. 2)via a set of startup control signal lines 340.

As will be described, mission critical hardware and software modules322, 332 can be switched on and started immediately upon the driverbeing detected to be inside a predetermined activation range relative tothe associated motor vehicle. The non-mission-critical modules 324, 334can be powered on and started at a later time in response to additionaltriggering events indicating that the driver will use the vehicleimminently. These triggers may include, for example, the driver doorbeing unlocked or opened, or the ignition is being turned on forexample.

The PMM of the example embodiment includes control logic 210 forimplementing a power management policy that is used in the exampleembodiment to govern when the hardware and software modules should bebooted up and down. This policy can be updated over the air by anInternet server or a server in the cloud for example. The cloud-basedserver can use information aggregated from multiple vehicles to optimizethe power management policy and then update the policies onboard eachvehicle.

A methodology 400 of operating the PMM in the ignition ON state 120(FIG. 1) of the associated motor vehicle is shown in a simplistic flowchart in FIG. 4 for ease of describing the example embodiment. While thevehicle is in the ignition ON state 120, the PMM 200 actively performsits functions in a PMM Active Mode #1 402 until all devices of theassociated motor vehicle are fully booted and operational. Once all ofthe devices are fully booted and operational at step 402, the PMM 200transitions into a PMM Sleep Mode #1 404 while the vehicle ignition ison. In the PMM Sleep Mode #1, hardware of the PMM 200 is powered on, butmost of its software is idle or in a low power sleep mode.

A methodology 500 of operating the PMM in the ignition OFF state 110(FIG. 1) of the associated motor vehicle is shown in a simplistic flowchart in FIG. 5 for ease of describing the example embodiment. When thevehicle is in the ignition OFF state, a decision is made at 502 whetherthe PMM 200 should either remain in a PMM Active Mode #2 504continuously or alternate between the PMM Active Mode #2 504 and a PMMSleep Mode #2 506. Alternating between the PMM Active Mode #2 504 andthe PMM Sleep Mode #2 506 consumes less power than operating in the PMMActive Mode #2 504 at all times and hence consumes less battery 310power.

A methodology 600 of operating the PMM in the PMM Active Mode #2 504(FIG. 5) during the ignition OFF state 110 (FIG. 1) of the associatedmotor vehicle is shown in a simplistic flow chart in FIG. 6 for ease ofdescribing the example embodiment. While the PMM 200 is in the PMMActive Mode #2 504 (FIG. 5) and the vehicle is in the ignition OFF state110, the control logic 210 of the PMM 200 executes a Driver ProximityDetection Procedure 602 to detect whether a driver of the associatedmotor vehicle is inside or otherwise within a predetermined activationrange relative to the associated motor vehicle. In an exampleembodiment, the activation range is a predefined distance from thevehicle. If the driver is detected to be inside the activation range atstep 604, the PMM remains in PMM Active Mode #2 and initiates a Hardwareand Software Startup and Management Procedure 610. If, however, thedriver is not detected to be within the activation range, the controllogic 210 of the PMM 200 initiates a PMM Sleep Mode PreparationProcedure 620 to determine when and how long the next PMM Sleep Mode #2506 (FIG. 5) should be.

The control logic 210 of the PMM 200 is operable to selectively executethe Driver Proximity Detection Procedure 602 to detect the driver'sproximity to the vehicle and use the detection results to help determinewhether and when to power on the device hardware modules 322, 324 andstart the device software and application modules 332, 334 (FIG. 3). Inthe example embodiment, the Driver Proximity Detection Procedure 602monitors radio transmissions from mobile devices such as those that maybe carried by the driver, to detect how close the driver is to theassociated vehicle or to the PMM 200. The driver's mobile device can be,for example, a key fob, smartphone, or the like.

In accordance with the example embodiment, different approaches can beused by the control logic 210 of the PMM 200 to use the driver's mobiledevices to detect the driver's proximity. In an example embodiment, anapplication on the driver's mobile device periodically broadcasts aradio beacon, which is monitored by components of the PMM 200. Inanother example embodiment, the control logic 210 of the PMM 200periodically broadcasts radio beacons which, when received by thedriver's mobile device, triggers the mobile device to transmit messagesto the PMM over a radio link. The radio beacons can be transmitted usingany available radio technology such as unlicensed RF, WiFi, Bluetooth,Dedicated Short Range Communications (DSRC), or the like. In yet afurther example embodiment, the control logic 210 of the PMM 200 usesregular cellular radio transmissions from the driver's smartphone todetect the relative proximity of the driver to the vehicle. In yet astill further example embodiment, the driver may use a mobile phone tosend messages to the PMM 200 to instruct the control logic 210 of thePMM to boot up one or more selected devices 300 of the associated motorvehicle.

In the example embodiment, the PMM 200 uses the radio signals from thedriver's mobile device to estimate the driver's proximity to the vehiclewithout necessarily requiring the driver's mobile devices to sendexplicit positioning information. For example, certain short rangeradios, such as the radio used by most vehicle key fobs, are capable oftransmitting such a short distance that the PMM is only be able toreceive their radio signals when the key fobs are within a couple ofmeters of the vehicles. The PMM 200 may also apply more sophisticatedsignal processing techniques as necessary or desired such as might berequired for example in certain applications to analyze the radiosignals received from a driver's mobile devices to estimate theproximity of these mobile devices to the vehicle. Furthermore, the radiobeacons from the driver's mobile devices can also carry explicitinformation about the position of the transmitting device to help thePMM 200 determine the driver's proximity.

The control logic 210 of the PMM may also access off-board locationservices to help determine how far away the driver is from the vehicle.The driver can update its location to a location server, in a periodicalor event-driven fashion. The PMM can retrieve the driver's last locationupdate from the location server. The driver's last reported location andthe elapsed time since the last location update can help the PMMestimate how long it may take the driver come to the activation rangeand hence how long the PMM 200 can wait in PMM Sleep Mode for the driverto arrive.

When the PMM 200 detects the driver to be within the activation range atstep 604, the control logic 210 of the PMM 200 initiates the Hardwareand Software Startup and Management Procedure 610 to power up the Devicehardware and to start its software and application modules.

On the other hand, when the PMM 200 fails to detect the driver to bewithin the activation range at step 604, the control logic 210 of thePMM 200 initiates the PMM Sleep Mode Preparation Procedure 620. Inaccordance with the example embodiment, the PMM Sleep Mode PreparationProcedure 620 uses a statistical modeling technique to predict when itshould transition into the PMM Sleep Mode #2 506 (FIG. 5) and how longit should stay in the Sleep Mode. The PMM transitions itself into the‘PMM Sleep Mode’ at time t and stays in the PMM Sleep Mode for up toT_(sleep) time units if it predicts that the driver is not likely to bewithin the activation range during time interval (t, t+T_(sleep)) andthis time interval is long enough (e.g., when it is sufficiently longerthan the time it takes to transition the PMM into ‘PMM Sleep Mode’ plusthe time it takes for the PMM to later wake up and enter ‘PMM ActiveMode’). Upon the expiration of the ‘PMM Sleep Mode,’ the PMM transitionsinto ‘PMM Active Mode’ to run the ‘Driver Proximity Detection Procedure’again.

In accordance with the embodiments, many different stochastic modelingtechniques can be used to predict the start time and the duration of thenext ‘PMM Sleep Mode.’ One example approach in accordance with theexample embodiment is as follows below.

Let T be the random variable that represents the time between twoconsecutive times the driver is detected to enter the activation range.Let t be the current time and assume the driver is not detected to beinside the activation range currently. To predict the time duration δbetween the current time t and the next time the driver is expected toenter the activation range, let P(δ) be the probability that T>(t+δ)given than T>t. That is

P(δ)=P(T>t+δ|T>t)

Let α be the confidence level of the prediction, where α is a percentageup to 100%, the maximal duration T_(sleep) that the PMM can stay in the‘PMM Sleep Mode’ next time can be estimated as

T _(sleep)=max{δ|P(δ)≧α}

This means there is a percent certainty the driver will not enter theactivation range during the next T_(sleep) time units. Therefore, ifT_(sleep) is significantly longer than the time it takes for the PMM totransition into ‘PMM Sleep Mode’ plus the time it takes for the PMM tolater wake up to enter ‘PMM Active Mode’ again, the PMM can enter ‘PMMSleep Mode’ at some time in [t, t+T_(sleep)) and should wake up beforetime t+T_(sleep).

In the example embodiment, (1−α) represents the probability that aprediction is wrong, which means that the device will be powered upprematurely. The value of a is configurable however. A small value of awill significantly reduce the amount of unnecessary device boot ups andthe amount of unnecessary wait time a device will experience each timeit is booted up.

In accordance with the embodiment, P(δ) is computed, wherein P(δ) isestimated based on the durations the PMM has been in ‘PMM Sleep Mode’ inthe past. For example, the PMM can maintain a histogram of the pastvalues of ‘PMM Sleep Mode’ durations with bin width equal to the unittime. Let H(n) denote the value of the n^(th) bin in this histogram.Then P(δ) can be estimated as follows, where N is the total number ofbins in the histogram:

${P(\delta)} = \frac{\sum\limits_{i = {t + \delta}}^{N}{H(i)}}{\sum\limits_{i = t}^{N}{H(i)}}$

In practice, typically 25 to 30 samples of past durations the PMM hasstayed in the ‘PMM Sleep Mode’ will be sufficient to derive adequateestimates.

It is to be appreciated that the PMM is not limited to the describedmethodologies but rather that other example embodiments can also useother stochastic models to predict its sleep durations. For example,time series analysis using Autoregressive Integrated Moving Average(ARIMA) models can be used to predict the next sleep duration bymodeling the correlations among recent sleep durations. The Wienerprocesses may also be used, which predict the next value of a stochasticprocess based on its most recent past value and statistics derived fromits recent past samples.

FIG. 7 is a high level block diagram showing a functional flow 700 ofthe PMM in an Active Mode in accordance with an example embodiment. Thehardware and software startup and management procedure 610 of the PMM200 described above is responsive to a set of selected externaloverriding and/or triggering events 710 to enter into the driverproximity detection procedure 602 as described above. In one functionalflow 720, the trigger events include the device or the software of thedevice and its applications being powered off or being in a power-savingmode. The trigger events may also include the PMM determining on its ownfor various reasons to initiate the driver proximity detection procedure602. In another functional flow 722, the trigger event includes theignition of the associated vehicle being turned off.

The functional flows 720, 722 may be selectively reversed in flow 724when the user of the associated vehicle is detected to be within apredetermined proximity or an activation range of the vehicle, or when astatistical value S calculated estimating a probability of the usermoving towards the vehicle or about to initiate operation of the vehicleexceeds a predetermined threshold. For these events, the flow 724 causesthe PMM to transition from the driver proximity detection procedure 602to the hardware and software startup and management procedure 610.

The PMM 200 selectively transitions from the driver proximity detectionprocedure 602 to a procedure for powering off all hardware and softwaremodules 320, 330 and entering into a delay 730 in accordance withtrigger events at functional flow 732 including the user of the vehiclenot being in the activation range, the statistical value S not beingexceeded, or the hardware and timer expiring. From this procedure 730the PMM may selectively enter into the sleep mode preparation procedure620 described above in connection with FIG. 6 after a predetermineddelay period. Thereafter, a functional flow 740 may be caused bytriggering events including a determination by the PMM of aninsufficient time being available for sleeping. The PMM may transitionat 750 to the sleep mode however, in accordance with a determination ofa sufficient time being available for sleeping.

FIG. 8 is a control diagraph showing operation of the PMM in accordancewith an example embodiment showing in particular workings of thehardware and software startup and management procedure 610 in accordancewith the example embodiment. The functional events and actions 800illustrated in this diagraph is by way of example only and is notintended to limit the operation of any alternative embodiments. Withreference now to that Figure, the PMM 200 is responsive to a set of oneor more triggering and/or overriding event(s) 810 such as for example atriggering and overriding event indicating that the user of theassociated vehicle will imminently start the vehicle. The PMM executes afirst procedure 820 for initiating power on to mission critical hardwaremodules 322 and the mission critical software modules 332. Thereafter,the PMM executes a delay procedure 822 until receiving a triggerindicating one or more triggering and/or an overriding event(s) 810 toexecute at 824 a procedure for initiating power on to missionnon-critical hardware modules 324 and the mission non-critical softwaremodules 334.

For purposes of describing the example embodiment, overriding events areany one or more event(s) or combinations of any events that areunexpected for the state or mode that the PMM is in. As an example, ifthe PMM detects the opening of the driver's door of the vehicle withoutdetecting the close proximity of any driver to the vehicle, both of thefirst and second procedures 820, 824 are initiated for administeringpower on to the mission critical hardware and to the missionnon-critical hardware, respectively. In accordance with a furtherexample, the detection of an “ignition on” condition regardless of thestate or mode the PMM is in trigger initiations of the first and secondprocedure 820, 824 as well. Thereafter the PMM may enter into a delaymode or state 852 described below.

The PMM 200 executes at 830 a procedure to wait for a predetermined timeperiod until the ignition of the associated vehicle is turned on, untilone or more other triggering and/or overriding events are determined, oruntil a time period expires wherein the time period is statisticallydetermined using one or more of the stochastic modeling techniquesdescribed above. When the wait time period of the procedure 830 isexceeded, the PMM functional flow 840 next executes a delay at 842 untilentering into the driver proximity detection procedure 602 describedabove in connection with FIG. 6. Alternatively, the PMM functional flow850 executes a delay at 852 until the ignition of the associated vehicleis turned off and the user leaves the activation region before enteringinto the driver proximity detection procedure 602. It is to beappreciated that in accordance with the example embodiments herein, thewait and delay periods executed by the PMM in the several modes orstates are for selected time periods preferably determined statisticallyusing any one or more of the stochastic modeling techniques describedabove.

FIG. 9 is a chart showing several operational modes 900 of the PMM 200in accordance with an example embodiment. Example uses of power modes900 and transitions from one power mode to another are shown. It is tobe appreciated, however, that other power modes and other transitionsand transition triggering or overriding events are possible inaccordance with further embodiments herein.

In FIG. 9, the several power modes 900 are illustrated plotted against atime axis 902 and a total energy consumption axis 904 for ease ofdescription and understanding. In addition, a set of five (5) modes 900are illustrated including a Full Active Mode 910, a Power Saving Mode 1912, a Power Saving Mode 2 914, a Power Saving Mode 3 916, and a PowerSaving Mode 4 912.

In accordance with the example embodiment, the mission critical hardwaremodules 322, the non-mission critical hardware modules 324, the missioncritical software modules 332, and the non-mission critical softwaremodules 334 are separately controlled by the control logic 210 of thePMM 200 in the set of five (5) modes described. However, the devices ofthe associated vehicle can be controlled in several other combinationsas may be necessary or desired.

In the simplistic example shown in the Figure, in accordance with theexample embodiment, at a transition from the Full Active Mode 910 to thePower Saving Mode 1 912, non-mission critical software modules areturned off by the PMM 200. At a transition from the Power Saving Mode 1912 to the Power Saving Mode 2 914, all software modules are turned offby the PMM 200. At a transition from the Power Saving Mode 2 914 to thePower Saving Mode 3 916, non-mission critical hardware modules areturned off by the PMM 200. At a transition from the Power Saving Mode 3916 to the Power Saving Mode 4 918, all hardware modules are turned offby the PMM 200. It is to be appreciated that the total energyconsumption 904 is decreased at each transition, and the wait time 902between transitions increases.

Further in the example embodiment shown in FIG. 9, at a transition fromthe Power Saving Mode 4 918 to the Power Saving Mode 3 916, all hardwaremodules are turned on by the PMM 200. At a transition from the PowerSaving Mode 3 916 to the Power Saving Mode 2 914, non-mission criticalhardware modules are turned on by the PMM 200. At a transition from thePower Saving Mode 2 914 to the Power Saving Mode 1 912, all softwaremodules are turned on by the PMM 200. Lastly, at a transition from thePower Saving Mode 1 912 to the Full Active Mode 910, non-missioncritical software modules are turned on by the PMM 200. It is to beappreciated that the total energy consumption 904 is increased at eachtransition, and the wait time 902 between transitions decreases.

As noted above, the device hardware modules 320 are grouped intomission-critical 322 and non-mission-critical 324 modules (FIG. 3). Thepower to the mission-critical modules and the non-mission-criticalmodules is controlled by separate switches 302 and 31, 318 on the powersupply line from the associated vehicle battery 310. Similarly, thesoftware and application modules 330 on the device are grouped intomission-critical 332 and non-mission-critical 334 modules in a way thatmission-critical software modules 332 can be started beforenon-mission-critical software modules 334.

Mission critical hardware and software modules can be switched on andstarted immediately upon the driver is detected to be inside theActivation Range. The non-mission-critical modules can be powered on andstarted at a later time in response to additional triggering and/oroverriding events indicating that the driver will use the vehicleimminently. These triggers include, for example, the driver door isunlocked or opened, or the ignition is being turned on (FIG. 8).

In accordance with the example embodiment, the control logic 210executes a power management policy to govern when power should beapplied to the hardware modules and when the software modules should bebooted up and/or down. This policy may be selectively updated over theair by a server in the cloud. The cloud-based server can use informationaggregated from multiple vehicles as necessary or desired to optimizethe power management policy and then update the policies onboard eachvehicle.

To further ensure that one or more selected devices of the associatedvehicle will be switched on in a timely fashion in accordance with theembodiments herein, the control logic 210 of the PMM 200 considers notonly whether the driver is inside the Activation Range but also otherfactors that can help determine how soon the vehicle may need to beturned on. These factors include, for example, whether the driver isapproaching the vehicle or moving away from it. In this regard, inaccordance with an example embodiment, S is used to denote thelikelihood that the vehicle will be keyed on each time the driver isdetected to be inside the Activation Range. The value of S ranges from 0to 1. The control logic 210 of the PMM 200 estimates the value of S eachtime it detects the driver to be inside the Activation Range and turnson a device of the set 300 of devices of the associated vehicle when theS value exceeds a predefined threshold. A default approach of theexample embodiment is to set S to 1 as soon as the driver is detectedinside the Activation Range, which means that the device will beswitched on as soon as the driver is detected to be inside theActivation Range.

More sophisticated approaches in accordance with further exampleembodiments take into account other factors to estimate the value of S.For example, the control logic 210 of the PMM 200 monitors the strengthof the direct short range radio between the driver's mobile device andthe PMM. An increasing signal strength indicates that the driver isapproaching the vehicle and hence a higher value of S. A faster increasein the signal strength indicates a higher speed in which the driver ismoving toward the vehicle and hence a higher value of S. Conversely,decreasing signal strength indicates that the driver is moving away fromthe vehicle. Using this approach, S is modeled by the control logic 210of the PMM 200 as a function of the driver's distance to the vehicle andthe change in the signal strength of the driver's mobile device.

The driver can also be inside the Activation Range for an extendedperiod of time with no intention to actually start the car. In suchcases, it may be unnecessary to hold or otherwise maintain the one ormore devices of the associated vehicle fully powered on or have itssoftware and application modules running. Therefore, multiplepower-saving modes 900 are applied by the control logic 210 of the PMM200. In accordance with the example embodiment, after any subset of thehardware modules on the one or more devices of the associated vehicle isswitched on, the PMM monitors how long it has been waiting until thevehicle ignition is turned on and uses the results to determine whichpower mode the device should enter and how long the device should stayin each power mode. Any one or more of the statistical modelingapproaches as described above may be used by the control logic 210 ofthe PMM 200 to determine when to start its own PMM Sleep Mode and howlong it should stay in the PMM Sleep Mode. The stochastic modelingtechniques described herein are used to predict how long the device willwait for the vehicle ignition to be turned on.

While waiting for the ignition to be turned on, the device of theassociated vehicle may stay in one of the power modes for apredetermined residence time. Alternatively, the control logic 210 ofthe PMM 200 uses a statistical modeling technique to dynamicallyestimate the residence time of the device for each power mode based onhistorical data it has collected regarding how long the device stayed inthis power mode in the past. This includes predicting when the deviceand the application modules on it should be started up and when theyshould enter full active mode. This allows the device and theapplication modules on it to be able to spend the least possible time totransition into fully active mode when needed. The prediction can beachieved using any one or more of the statistical models used by the PMMas described above to estimate the starting times and the durations forits own PMM Sleep Mode 2 506 (FIG. 5).

The methods used herein in accordance with the example embodiments todetermine how long the device will have to wait for the vehicle ignitionto be turned on and how long the device should stay in each power modefurther take into account additional contextual information such as thelocation of the associated vehicle and the time of day. For example, acondition of the vehicle being parked inside a garage and the mobiledevice of the driver being inside the house but away from the garage,can be sufficient close to the vehicle to trigger device wakeup.Therefore, in an example embodiment, the control logic 210 of the PMM200 dynamically adjusts the threshold of the activation range dependingon the location of the vehicle and other contextual information.

The one or more devices of the associated vehicle can be controlledresponsive to triggering and overriding events to transition from onepower mode to another. Overriding events are events that will triggerthe one or more devices to change their power mode. For example, theIgnition-On event should trigger the device to transition into a fullactive mode immediately.

FIG. 10 is a state transition diagraph showing several power modes ofthe PMM in accordance with an example embodiment. With reference now tothat Figure, the PMM 200 may transition from any one of the power savingmodes 1-3912-918 in response to one or more overriding events 1002-1008such as, for example, the transition of the ignition key from the ONcondition 110 (FIG. 1) to the OFF condition 120.

In addition, in accordance with the embodiments, each time the vehicleignition is turned off, the PMM transitions state from PMM Sleep Mode #1404 (FIG. 4) to the PMM Active Mode #2 504 (FIG. 5). It then waits forthe driver to exit the Activation Range, or the S value to fall belowthe threshold, or a wait timer expires, to shut down all hardware andsoftware modules and initiate the PMM Sleep Mode Preparation Procedure620 (FIG. 6) to determine whether and when the PMM should enter PMMSleep Mode #2 506 and for how long the PMM should reside in the PMMSleep Mode #2 506.

The control logic 210 of the PMM 200 selectively transitions between thePower Saving Modes 912-918 in accordance the expiration of apredetermined residence time spent in the current state. For example,the PMM may transition from the Power Saving Mode 1 912 to the PowerSaving Mode 2 914 at 1010 upon the expiration of a timer set forresidence in the Power Saving Mode 1 912. Similarly, the PMM maytransition from the Power Saving Mode 2 914 to the Power Saving Mode 1912 at 1012 upon the expiration of a timer set for residence in thePower Saving Mode 2 914. The one or more wait timer values can be presetor dynamically estimated using the same statistical model the PMM usesto estimate the length of its own ‘PMM Sleep Mode’. Similar state modetransitions 1020, 1022, and 1024 are selectively executed by the PMM 200as well.

In accordance with an embodiment, each time the PMM enters the ‘PMMSleep Mode’, it stays in this mode for either a predefined ordynamically estimated time duration before it wakes up to resume theDriver Proximity Detection 602 procedure. Any one or more of thestatistical models used by the PMM to estimate the starting times andthe lengths of its own ‘PMM Sleep Mode’ as described above are used toestimate the length of this random delay.

In accordance with further example embodiments, while themission-critical hardware and software modules are booted up and thedevices are waiting for the vehicle ignition to be turned on, the PMM isoperative to determine whether the CPU clock speed of the device shouldbe lowered or otherwise reduced to further reduce battery powerconsumption by the device. If the PMM determines to lower the device'sclock speed, it sends a signal to a control software on the device totrigger it to lower the device's CPU clock speed. This signal triggersthe device's CPU clock to be lowered after the mission critical softwaremodules finish their initialization procedures. The CPU clock of thedevice returns to its normal speed when the device is triggered by anyevent to boot up its non-mission-critical hardware and software modules.Additionally, if the hardware allows, the same mechanism can also beused to lower operating voltage of the device. Different modalities ofchanging operating frequency and voltage can be implemented. Thistechnique of reducing clock speed and operating voltage can result infurther reduction of standby power while keeping the system almost readyto jump into fully activated mode.

FIG. 11 is a further example state transition diagram between powermodes of the PMM in accordance with an embodiment. With reference now tothat Figure, the first and third power saving modes 912, 916 form afirst super power saving mode 1102 wherein all non-critical hardware andsoftware modules 324, 334 are turned OFF. Also, a second super powersaving mode 1104 is formed wherein all comprising the second and fourthpower saving modes 914, 918 wherein all hardware and software modules320, 330 are turned OFF. The PMM may transition directly from the fullactive mode 910 to the second super power saving mode 1104 at 1110responsive to a first overriding event. Conversely, the PMM maytransition directly from the second super power saving mode 1104 to thefull active mode 910 at 1112 responsive to a second overriding event.Further, the PMM may transition indirectly from the second super powersaving mode 1104 to the full active mode 910 at 1120 and 1122 by firstpassing through the first super power saving mode 1102 responsive tothird and fourth overriding events.

Further in addition to the above, the PMM may transition between thefull active mode 910 and the first and second super power saving modes1102, 1104 the upon the expiration of one or more timer set forresidence in the Power Saving Modes. In this regard, the PMM maytransition from the full active mode 910 to the first super power savingmode 1102 at 1130 responsive to the expiration of a first predeterminedresidence time. The PMM may transition from the first super power savingmode 1102 to the second super power saving mode 1104 at 1132 responsiveto the expiration of a second predetermined residence time. The PMM maytransition from the second super power saving mode 1104 to the firstsuper power saving mode 1102 at 1140 responsive to the expiration of athird predetermined residence time. Lastly, the PMM may transition fromthe first super power saving mode 1102 to the full active mode 910 at1142 responsive to the expiration of a fourth predetermined residencetime. The same statistical model used by the PMM to estimate thestarting times and the lengths of its own ‘PMM Sleep Mode’ as describedabove are used to estimate the length of the first through fourthresidence times.

FIG. 12 is a block diagram illustrating an example of a computer system1200 upon which an example embodiment can be implemented. Computersystem 1200 may be employed to implement the functionality of the logicin controller 110 (FIG. 1), the control logic 210 of the access point200 (FIG. 2), and/or the gateway logic 310 in the enterprise networkcontroller apparatus 300 (FIG. 3).

Computer system 1200 includes a bus 1202 or other communicationmechanism for communicating information and a processor 1204 coupledwith bus 1202 for processing information. Computer system 1200 alsoincludes a main memory 1206, such as random access memory (RAM) or otherdynamic storage device coupled to bus 1202 for storing information andinstructions to be executed by processor 1204. Main memory 1206 also maybe used for storing a temporary variable or other intermediateinformation during execution of instructions to be executed by processor1204. Computer system 1200 further includes a read only memory (ROM)1208 or other static storage device coupled to bus 1202 for storingstatic information and instructions for processor 1204. A storage device1210, such as a magnetic disk, optical disk, and/or flash storage, isprovided and coupled to bus 1202 for storing information andinstructions.

An aspect of the example embodiment is related to the use of computersystem 1200 for providing detection of service instances available in anetwork, caching the detected network service instances, and advertisingthe cached detected network services to client devices in accordancewith a physical location of the querying client device in a locationaware service instance utility. According to an example embodiment,detecting, caching, and advertising network service instances isprovided by computer system 1200 in response to the processor 1204executing one or more sequences of one or more instructions contained ina non-transitory main memory 1206. Such instructions may be read intomain memory 1206 from another computer-readable medium, such as storagedevice 1210. Execution of the sequence of instructions contained in mainmemory 1206 causes processor 1204 to perform the process steps describedherein. One or more processors in a multi-processing arrangement mayalso be employed to execute the sequences of instructions contained inmain memory 1206. In alternative embodiments, hard-wired circuitry maybe used in place of or in combination with software instructions toimplement an example embodiment. Thus, embodiments described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The term “computer-readable medium” as used herein refers to anynon-transitory medium that participates in providing instructions toprocessor 1204 for execution. Such a medium may take many forms,including but not limited to non-volatile media, and volatile media.Non-volatile media include for example optical or magnetic disks, suchas storage device 1210. Volatile media include dynamic memory such asmain memory 1206. As used herein, tangible media may include anynon-transitory media such as a volatile and non-volatile media. Commonforms of computer-readable media include for example floppy disk, aflexible disk, hard disk, magnetic cards, paper tape, any other physicalmedium with patterns of holes, a RAM, a PROM, an EPROM, a FLASHPROM, CD,DVD or any other memory chip or cartridge, or any other medium fromwhich a computer can read.

Various forms of computer-readable media may be involved in carrying oneor more sequences of one or more instructions to processor 1204 forexecution. For example, the instructions may initially be borne on amagnetic disk of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 1200 canreceive the data on the telephone line and use an infrared transmitterto convert the data to an infrared signal. An infrared detector coupledto bus 1202 can receive the data carried in the infrared signal andplace the data on bus 1202. Bus 1202 carries the data to main memory1206 from which processor 1204 retrieves and executes the instructions.The instructions received by main memory 1206 may optionally be storedon storage device 1210 either before or after execution by processor1204.

Computer system 1200 also includes a communication interface 1218comprising first and second communication interfaces 1220, 1222operatively coupled with the bus 1202. Communication interface 1218provides a two-way data communication coupling computer system 1200 to acommunication link 1230. For example, communication interface 1218 maybe a local area network (LAN) card to provide a data communicationconnection to a compatible LAN such as for example a Controller AreaNetwork (CAN) network. As another example, communication interface 1218may be an integrated services digital network (ISDN) card or a modem toprovide a data communication connection to a corresponding type oftelephone line. Wireless links may also be implemented. In any suchimplementation, communication interface 1218 sends and receiveselectrical, electromagnetic, or optical signals that carry digital datastreams representing various types of information.

Described above are example embodiments. It is, of course, not possibleto describe every conceivable combination of components ormethodologies, but one of ordinary skill in the art will recognize thatmany further combinations and permutations of the example embodimentsare possible. Accordingly, this application is intended to embrace allsuch alterations, modifications and variations that fall within thespirit and scope of the appended claims interpreted in accordance withthe breadth to which they are fairly, legally and equitably entitled.

1. An apparatus comprising: an interface operatively coupled with aplurality of power consuming devices of an associated power consumingsystem; and control logic coupled with the interface; wherein thecontrol logic is operable in a plurality of modes comprising at least afirst mode and a second mode; wherein the control logic is operable inthe first mode to perform processing for determining a presence of afirst condition of the associated power consuming system; wherein thecontrol logic is operable in the first mode to selectively activate oneor more of the plurality of power consuming devices of the associatedsystem, via the interface, responsive to determining the presence of thefirst condition; wherein the control logic is operable in the secondmode to suspend, via the interface, the processing for determining thepresence of the first condition of the associated power consumingsystem; wherein the control logic selectively transitions from the firstmode to the second mode and remains in the second mode in accordancewith a stochastic modeling of the presence of the first condition overtime.
 2. The apparatus according to claim 1, wherein: the control logicdetermines a start time for transitioning from the first mode to thesecond mode in accordance with the stochastic modeling of the presenceof the first condition over time; the control logic determines a timeduration for remaining in the second mode in accordance with thestochastic modeling of the presence of the first condition over time;and the control logic selectively transitions between the first andsecond modes in accordance with a current time, the determined starttime, and the determined time duration.
 3. The apparatus according toclaim 1, wherein: the control logic is operable, while in the firstmode, in a plurality of power saving modes comprising at least: i) afull active mode wherein the control logic activates the plurality ofpower consuming devices, and ii) a first power saving mode wherein thecontrol logic reduces a clock speed of a selected one or more of theplurality of power consuming devices of the associated system; and thecontrol logic selectively transitions between the full active mode andthe first power saving mode in accordance with a stochastic modeling ofa use condition of the associated power consuming system by anassociated user of the system over time.
 4. The apparatus according toclaim 1, wherein: the control logic is operable, while in the firstmode, in a plurality of power savings modes comprising at least: i) afull active mode wherein the control logic activates the plurality ofpower consuming devices, and ii) a first power saving mode wherein thecontrol logic reduces an operating voltage of a selected one or more ofthe plurality of power consuming devices of the associated system; andthe control logic selectively transitions between the full active modeand the first power saving mode in accordance with a stochastic modelingof a use condition of the associated power consuming system by anassociated user of the system over time.
 5. The apparatus according toclaim 1, wherein: the interface is operatively coupled with a first setof the plurality of power consuming devices of the associated system,and with a second set of plurality of power consuming devices of theassociated system; the control logic is operable, while in the firstmode, in a plurality of power savings modes comprising at least: i) afull active mode wherein the control logic selectively activates thefirst and second sets of the plurality of power consuming devices, andii) a first power saving mode wherein the control logic selectivelydeactivates at least one power consuming device of the first set of theplurality of power consuming devices or at least one power consumingdevice of the second set of the plurality of power consuming devices;and the control logic selectively transitions between the full activemode and the first power saving mode in accordance with a stochasticmodeling of a use condition of the associated power consuming system byan associated user of the system over time.
 6. The apparatus accordingto claim 1, wherein: the interface is operatively coupled with a firstset of plurality of power consuming devices comprising mission criticalpower consuming devices of the associated system; the interface isoperatively coupled with a second set of the plurality of powerconsuming devices comprising non-mission critical power consumingdevices of the associated system; the control logic is operable, whilein the first mode, in a plurality of power savings modes comprising atleast: i) a full active mode wherein the control logic activates thefirst and second sets of the plurality of power consuming devices of theassociated system, and ii) a first power saving mode wherein the controllogic reduces power to a selected one or more of the second set of theplurality of power consuming devices of the associated system; and thecontrol logic selectively transitions between the full active mode andthe first power saving mode in accordance with a stochastic modeling ofa use condition of the associated power consuming system by anassociated user of the system over time.
 7. The apparatus according toclaim 6, wherein: the first set of the plurality of power consumingdevices comprises at least one mission critical hardware module of theassociated power consuming system, and at least one mission criticalsoftware module of the associated power consuming system; the second setof the plurality of power consuming devices comprises at least onenon-mission critical hardware module of the associated power consumingsystem, and at least one non-mission critical software module of theassociated power consuming system; the control logic is operable, whilein the first mode, in a plurality of power savings modes comprising atleast: i) a full active mode wherein the control logic activates thefirst and second sets of the plurality of power consuming devices of theassociated system; ii) a first power saving mode wherein the controllogic activates the at least one mission critical hardware module, theat least one mission critical software module, and the at least onenon-mission critical hardware module, and deactivates the at least onenon-mission critical software module; iii) a second power saving modewherein the control logic activates the at least one mission criticalhardware module, the at least one non-mission critical hardware moduleand deactivates the at least one mission critical software module andthe at least one non-mission critical software module; iv) a third powersaving mode wherein the control logic activates the at least one missioncritical hardware module, and deactivates the at least one missioncritical software module, the at least one non-mission critical hardwaremodule and the at least one non-mission critical software module; and v)a fourth power saving mode wherein the control logic deactivates thefirst and second sets of the plurality of power consuming devices of theassociated system; the control logic selectively transitions between thefull active mode, the first power saving mode, the second power savingmode, the third power saving mode, and the fourth power saving mode inaccordance with a stochastic modeling of the use condition of theassociated power consuming system by an associated user of the systemover time.
 8. The apparatus according to claim 1, further comprising: atransceiver operatively coupled with the control logic; wherein thecontrol logic is operative to transmit, via the transceiver, datarepresentative of the first and second modes to an associated powermanagement policy server; wherein the control logic is operative toreceive from the associated power management policy server, via thetransceiver, data representative of an updated power management policy;wherein the control logic is operative to update the first and secondmodes as updated first and second modes in accordance with the receivedupdated management policy; wherein the control logic is operable in theupdated first mode to perform processing for determining a presence of afirst condition of the associated power consuming system; wherein thecontrol logic is operable in the updated first mode to selectivelyactivate one or more of the plurality of power consuming devices of theassociated system, via the interface, responsive to determining thepresence of the first condition; wherein the control logic is operablein the updated second mode to suspend, via the interface, the processingfor determining the presence of the first condition of the associatedpower consuming system; wherein the control logic selectivelytransitions from the updated first mode to the updated second mode andremains in the updated second mode in accordance with the stochasticmodeling of the presence of the first condition over time.
 9. Theapparatus according to claim 1, wherein: the control logic is operablein the first mode to selectively activate the plurality of powerconsuming devices of the associated system responsive to: i.)determining the presence of a predetermined one or more trigger events.10. The apparatus according to claim 1, wherein: the control logic isoperable in the first mode to selectively activate the plurality ofpower consuming devices of the associated system responsive to: i.)determining the presence of a user of the associated system within apredetermined activation range of the associated system and,selectively, ii) a likelihood S that the associated system will bepowered on each time the associated user enters into the predeterminedactivation range relative to the associated system or a rate of movementof the associated user above a predetermined threshold towards theassociated system.
 11. The apparatus according to claim 1, wherein: theinterface is operatively coupled with a plurality of power consumingdevices of an associated one or more of a motor vehicle, a home, anoffice building or a factory for selectively activating, while in thefirst mode, one or more of a plurality of power consuming devices of theassociated one or more of a motor vehicle, a home, an office building ora factory responsive to determining the presence of the first condition.12. A method comprising: operating control logic in a plurality of modescomprising at least a first mode and a second mode; performingprocessing by the control logic when operating in the first mode fordetermining a presence of a first condition of an associated powerconsuming system; selectively activation, by the control logic whenoperating in the first mode, one or more of a plurality of powerconsuming devices of the associated system, via an interface coupledwith the control logic and operatively coupled with the plurality ofpower consuming devices, responsive to determining by the control logicthe presence of the first condition; suspending, by the control logicwhen operating in the second mode, the processing for determining thepresence of the first condition of the associated power consumingsystem; and selectively transitioning the control logic from the firstmode to the second mode and remaining in the second mode in accordancewith a stochastic modeling of the presence of the first condition overtime.
 13. The method according to claim 12, further comprising:performing processing by the control logic to determine a start time fortransitioning from the first mode to the second mode in accordance withthe stochastic modeling of the presence of the first condition overtime; performing processing by the control logic to determine a timeduration for remaining in the second mode in accordance with thestochastic modeling of the presence of the first condition over time;and selectively transitioning the control logic between the first andsecond modes in accordance with a current time, the determined starttime, and the determined time duration.
 14. The method according toclaim 12, further comprising: operating the control logic, while in thefirst mode, in a plurality of power saving modes comprising at least: i)a full active mode wherein the control logic activates the plurality ofpower consuming devices, and ii) a first power saving mode wherein thecontrol logic reduces one or more of a clock speed, an operatingvoltage, or both the clock speed and the operating voltage of a selectedone or more of the plurality of power consuming devices of theassociated system; and selectively transitioning the control logicbetween the full active mode and the first power saving mode inaccordance with a stochastic modeling of a use condition of theassociated power consuming system by an associated user of the systemover time.
 15. The method according to claim 12, further comprising:operating the control logic, while in the first mode, in a plurality ofpower savings modes comprising at least: i) a full active mode whereinthe control logic activates first and second sets of the plurality ofpower consuming devices of the associated system, the first set ofplurality of power consuming devices comprising mission critical powerconsuming devices of the associated system and the second set of theplurality of power consuming devices comprising non-mission criticalpower consuming devices of the associated system, and ii) a first powersaving mode wherein the control logic reduces power to a selected one ormore of the second set of the plurality of power consuming devices ofthe associated system; and selectively transitioning the control logicbetween the full active mode and the first power saving mode inaccordance with a stochastic modeling of a use condition of theassociated power consuming system by an associated user of the systemover time.
 16. The method according to claim 15, further comprising:operating the control logic, while in the first mode, in a plurality ofpower savings modes comprising at least: i) a full active mode whereinthe control logic activates the first and second sets of the pluralityof power consuming devices of the associated system, wherein the firstset of the plurality of power consuming devices comprises at least onemission critical hardware module of the associated power consumingsystem and at least one mission critical software module of theassociated power consuming system, and the second set of the pluralityof power consuming devices comprises at least one non-mission criticalhardware module of the associated power consuming system and at leastone non-mission critical software module of the associated powerconsuming system; ii) a first power saving mode wherein the controllogic activates the at least one mission critical hardware module, theat least one mission critical software module, and the at least onenon-mission critical hardware module, and deactivates the at least onenon-mission critical software module; iii) a second power saving modewherein the control logic activates the at least one mission criticalhardware module, the at least one non-mission critical hardware moduleand deactivates the at least one mission critical software module andthe at least one non-mission critical software module; iv) a third powersaving mode wherein the control logic activates the at least one missioncritical hardware module, and deactivates the at least one missioncritical software module, the at least one non-mission critical hardwaremodule and the at least one non-mission critical software module; and v)a fourth power saving mode wherein the control logic deactivates thefirst and second sets of the plurality of power consuming devices of theassociated system; and selectively transitioning the control logicbetween the full active mode, the first power saving mode, the secondpower saving mode, the third power saving mode, and the fourth powersaving mode in accordance with a stochastic modeling of the usecondition of the associated power consuming system by an associated userof the system over time.
 17. Logic encoded in one or more tangiblenon-transient computer readable media for execution by a processor andwhen executed by the processor the logic being operable to: operatecontrol logic in a plurality of modes comprising at least a first modeand a second mode; perform processing by the control logic whenoperating in the first mode for determining a presence of a firstcondition of an associated power consuming system; selectively activate,by the control logic when operating in the first mode, one or more of aplurality of power consuming devices of the associated system, via aninterface coupled with the control logic and operatively coupled withthe plurality of power consuming devices, responsive to determining bythe control logic the presence of the first condition; suspend, by thecontrol logic when operating in the second mode, the processing fordetermining the presence of the first condition of the associated powerconsuming system; and selectively transition the control logic from thefirst mode to the second mode and remaining in the second mode inaccordance with a stochastic modeling of the presence of the firstcondition over time.
 18. The logic according to claim 17, furtheroperable to: perform processing by the control logic to determine astart time for transitioning from the first mode to the second mode inaccordance with the stochastic modeling of the presence of the firstcondition over time; perform processing by the control logic todetermine a time duration for remaining in the second mode in accordancewith the stochastic modeling of the presence of the first condition overtime; and selectively transition the control logic between the first andsecond modes in accordance with a current time, the determined starttime, and the determined time duration.
 19. The logic according to claim17, further operable to: operate the control logic, while in the firstmode, in a plurality of power saving modes comprising at least: i) afull active mode wherein the control logic activates the plurality ofpower consuming devices, and ii) a first power saving mode wherein thecontrol logic reduces one or more of a clock speed, an operatingvoltage, or both the clock speed and the operating voltage of a selectedone or more of the plurality of power consuming devices of theassociated system; and selectively transition the control logic betweenthe full active mode and the first power saving mode in accordance witha stochastic modeling of a use condition of the associated powerconsuming system by an associated user of the system over time.
 20. Thelogic according to claim 17, further operable to: operate the controllogic, while in the first mode, in a plurality of power savings modescomprising at least: i) a full active mode wherein the control logicactivates first and second sets of the plurality of power consumingdevices of the associated system, the first set of plurality of powerconsuming devices comprising mission critical power consuming devices ofthe associated system and the second set of the plurality of powerconsuming devices comprising non-mission critical power consumingdevices of the associated system, and ii) a first power saving modewherein the control logic reduces power to a selected one or more of thesecond set of the plurality of power consuming devices of the associatedsystem; and selectively transition the control logic between the fullactive mode and the first power saving mode in accordance with astochastic modeling of a use condition of the associated power consumingsystem by an associated user of the system over time.
 21. The logicaccording to claim 20, further operable to: operate the control logic,while in the first mode, in a plurality of power savings modescomprising at least: i) a full active mode wherein the control logicactivates the first and second sets of the plurality of power consumingdevices of the associated system, wherein the first set of the pluralityof power consuming devices comprises at least one mission criticalhardware module of the associated power consuming system and at leastone mission critical software module of the associated power consumingsystem, and the second set of the plurality of power consuming devicescomprises at least one non-mission critical hardware module of theassociated power consuming system and at least one non-mission criticalsoftware module of the associated power consuming system; ii) a firstpower saving mode wherein the control logic activates the at least onemission critical hardware module, the at least one mission criticalsoftware module, and the at least one non-mission critical hardwaremodule, and deactivates the at least one non-mission critical softwaremodule; iii) a second power saving mode wherein the control logicactivates the at least one mission critical hardware module, the atleast one non-mission critical hardware module and deactivates the atleast one mission critical software module and the at least onenon-mission critical software module; iv) a third power saving modewherein the control logic activates the at least one mission criticalhardware module, and deactivates the at least one mission criticalsoftware module, the at least one non-mission critical hardware moduleand the at least one non-mission critical software module; and v) afourth power saving mode wherein the control logic deactivates the firstand second sets of the plurality of power consuming devices of theassociated system; and selectively transition the control logic betweenthe full active mode, the first power saving mode, the second powersaving mode, the third power saving mode, and the fourth power savingmode in accordance with a stochastic modeling of the use condition ofthe associated power consuming system by an associated user of thesystem over time.